fix(release): satisfy npm provenance so packages actually publish#18
Merged
Conversation
The publish run went green while every npm publish silently failed with E422: provenance validation requires repository.url to match the repo the workflow runs from, and the generated platform/meta manifests had no repository field at all (the sdk and plugin manifests likewise), while the root and launcher manifests pointed at the wrong-case repo path. - stamp repository into the generated platform and wrapper manifests - add repository to the sdk and plugin packages - normalize existing repository URLs to the canonical lowercase path - release orchestration now records per-section failures and exits non-zero, so a green publish run means packages really shipped
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The publish workflow ran green while every npm publish silently failed with:
With
NPM_CONFIG_PROVENANCE=true, npm requires every published manifest'srepository.urlto match the repository the workflow runs from — case-sensitively. The generated platform/meta manifests had no repository field, sdk/plugin had none either, and root/launcher used a different-case path.repositoryinto the generated platform + wrapper manifests (build/publish scripts)repositoryto the sdk and plugin packagesVerified: turbo typecheck clean. The v1.2.3 GitHub release with all 11 platform archives already shipped from the previous run; nothing was published to npm at 1.2.3, so re-dispatching after this merge will cleanly publish 1.2.3 everywhere.